System for performing firmware updates on a number of drives in an array with minimum interruption to drive i/o operations

ABSTRACT

The present invention concerns an apparatus comprising a management utility and a processing utility. The management utility may be implemented on a host computer and be configured to initiate a request to apply a firmware update to a plurality of drives in an array. The processing utility may be implemented on a drive controller and may be configured to (i) determine which of the plurality of drives are in an idle state, (ii) send the firmware update to the drives determined to be in the idle state and (iii) repeat (i) and (ii) until all of the drives have been updated.

FIELD OF THE INVENTION

The present invention relates to drive arrays generally and, more particularly, to a method and/or apparatus for performing drive firmware updates on a number of drives in an array with minimum interruption to drive input/output (I/O) operations.

BACKGROUND OF THE INVENTION

In conventional drive arrays, drive firmware updates are carried out without monitoring input/output (I/O) activity on the drives. In such systems, a customer (or end user) can initiate a drive update of the firmware at any point using a management application. With such an implementation, there is a risk that the firmware updates lead to data corruption or I/O timeouts if there is heavy I/O traffic on the drives during such firmware updates.

It would be desirable to implement a method and/or apparatus for performing firmware updates to a number of drives in an array with minimum interruptions to drive input/output (I/O) operations.

SUMMARY OF THE INVENTION

The present invention concerns an apparatus comprising a management utility and a processing utility. The management utility may be implemented on a host computer and be configured to initiate a request to apply a firmware update to a plurality of drives in an array. The processing utility may be implemented on a drive controller and may be configured to (i) determine which of the plurality of drives are in an idle state, (ii) send the firmware update to the drives determined to be in the idle state and (iii) repeat (i) and (ii) until all of the drives have been updated.

The objects, features and advantages of the present invention include providing a system for performing drive updates that may (i) be implemented on a number of drives in an array, (ii) be implemented with a minimum of interruption to I/O activity and/or (iii) provide one or more safeguards if drive activity occurs.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features and advantages of the present invention will be apparent from the following detailed description and the appended claims and drawings in which:

FIG. 1 is a diagram of an example context of the present invention;

FIG. 2 is another diagram of a context of the present invention;

FIG. 3 is a flow diagram of an example implementation of the present invention;

FIG. 4 is a flow diagram illustrating more details of the initialization step of FIG. 2; and

FIG. 5 is a diagram of a table illustrating a structure for a firmware update.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Referring to FIG. 1, a block diagram of a system 100 is shown illustrating a context of the present invention. The system 100 generally comprises a block (or circuit) 102, a network 104, a block (or circuit) 106 and a block (or circuit) 108. The circuit 102 may be implemented as a host. The host 102 may be implemented as one or more computers in a host/client configuration. The host 102 may include a block (or module, or circuit) 107. The block 107 may be implemented as a management utility. The circuit 106 may be implemented as an enclosure. The enclosure 106 may include a number of storage devices (e.g., a drive array). The circuit 108 may be implemented as a controller. In one example, the circuit 108 may be a RAID (Redundant Array of Inexpensive Drives) controller. The circuit 108 may include a block (or module, or circuit) 109. The block 109 may be implemented as firmware that may control the controller 108. The block 109 may also include a processing utility that may operate in conjunction with the management utility 107 to implement the firmware updates discussed.

The host 102 may have an input/output 110 that may present a input/output request (e.g., REQ). The signal REQ may be sent through the network 104 to an input/output 112 of the controller 108. The controller 108 may have an input/output 114 that may present a signal (e.g., CTR) to an input/output 116 of the storage array 106.

The storage array 106 may have a number of storage devices (e.g., drives or volumes) 120 a-120 n, a number of storage devices (e.g., drives or volumes) 122 a-122 n and a number of storage devices (e.g., drives or volumes) 124 a-124 n. In one example, each of the storage devices 120 a-120 n, 122 a-122 n, and 124 a-124 n may be implemented as a single drive, multiple drives, and/or one or more drive enclosures. The storage devices 120 a-120 n, 122 a-122 n and/or 124 a-124 n may be implemented as one or more hard disc drives (HDDs), one or more solid state devices (SSDs) or a combination of HDDs and SSDs. In one example, the storage devices 120 a-120 n may be implemented as Fibre Channel (FC) drives. In one example, the storage devices 122 a-122 n may be implemented as Serial Advanced Technology Attachment (SATA) drives. In one example, the storage devices 124 a-124 n may be implemented as Serial Attached SCSI (SAS) drives. The system 100 may comprise a heterogeneous matrix of drives. The storage devices 120 a-120 n may have a corresponding firmware block 128 a-128 n. The storage devices 122 a-122 n may have a corresponding firmware block 130 a-130 n. The storage devices 124 a-124 n may have a corresponding firmware block 132 a-132 n. Redundancy may be provided if the data is striped across the drives 120 a-120 n, 122 a-122 n, and/or 124 a-124, such as in RAID 1, RAID 50, RAID 60, RAID 30, RAID 10 and/or RAID 01 volume groups.

Referring to FIG. 2, a diagram of a system 100′ is shown where the host is connected directly to the controller 108. Such a topology may be implemented as a Directly Attached Storage (DAS) configuration. The topology of FIG. 1 may be implemented as a Storage Area Network/Network Attached Storage (SAN/NAS) configuration. In the example shown, the host 102 is shown connected to the controller 108. However, in another example, the controller 108 may be implemented as a plug-in card that may be plugged into the host 102. The particular type of connection between the controller 108 and the host 102 may be varied to meet the design criteria of a particular implementation.

Referring to FIG. 3, a flow diagram of a method 200 is shown. The method 200 generally comprises a step (or state) 204, a step (or state) 206, a step (or state) 208, a step (or state) 210, a step (or state) 212, a decision step (or state) 214, a step (or state) 216 and a step (or state) 218. The step 202 may be a start step. The step 204 may be an initialization step. The step 206 may be a decision step. The step 208 may send a message that the firmware has been successfully updated. The step 210 may be a timer state. The step 212 may initialize the update of the drive firmware. The decision step 214 may determine whether the drive update has been successful. If so, the method 200 moves back to the state 206 to determine if all the drives have been successfully updated. If not, the method 200 moves to the state 216. The state 216 may send a firmware update fail message to an administrator through the management utility 107. The state 218 may be in an end state.

The state 208 comprises a decision step (or state) 230, a step (or state 232, and a decision step (or state) 234. The decision step 230 may determine if all of the selected drives have the updated firmware already updated. If so, the method 204 moves to the state 208. If not, the step 232 checks the status of the selected drives. Next, the decision step 234 determines if the selected drive is in an idle (or power down) mode. If so, the method 204 moves to the state 212 which initiates the drive firmware update. If not, the method 204 moves to the state 210.

The step 210 generally comprises a step (or state) 240, a decision step (or state) 242 and a step (or state) 244. The step 240 may maintain a timer configured to wait for a particular drive to enter a power down (or power save) mode. The decision step 242 determines whether a timer for each of the drives has expired. If so, the step 244 waits until the I/O activity on a particular drive becomes less than a predetermined amount (e.g., 30%). Next, the method 200 moves to the state 212. The timer state 210 may be implemented individually for each of the plurality of drives.

Referring to FIG. 4, a more detailed diagram of the step 204 is shown. The step 204 generally comprises the sub-steps of a step (or state) 260, step (or state) 262, step (or state) 264, step (or state) 266, step (or state) 268. The step 260 may implement a user login to the management utility 107. The step 262 may allow a user to select which of the drives 120 a-120 n, 122 a-122 n, and/or 124 a-124 the user intends to update. The step 264 may select a particular one of the drives 120 a-120 n, 122 a-122 n, and/or 124 a-124 that the firmware needs to be updated. The step 266 may browse for a particular firmware file. The step 268 may perform a firmware version comparison of each of the drives 120 a-120 n, 122 a-122 n, and/or 124 a-124 with the version of the firmware file. In general, the steps 260, 262, 264 and/or 266 may be performed on the management utility 107. The step 268 may also be performed on the management utility 107, but may have input received from the firmware 109 on the controller 108. The steps 206, 208, 210, 212, 214 and 216 may be performed on the firmware 109.

The method 200 may target a time to perform updates to the firmware 128 a-128 n, 130 a-130 n, and/or 132 a-132 n of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n when in “Power Save” mode. By targeting a time when the drives are in an idle (or power save) mode, the method 200 normally avoids potential data corruption and/or I/O time outs which could potentially occur if the update is performed while heavy I/O is being performed. If one or more of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n does not enter into Power Save mode after a significant time (e.g., a defined /pre-set time by user), the firmware update will be performed when the I/O activity on a particular one of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n is less than a pre-set threshold (e.g., 30%). While a 30% threshold is described as an example, the particular pre-set threshold may be varied to meet the design criteria of a particular implementation.

Referring to FIG. 5, a diagram illustrating a data structure for updating the firmware is shown. The first column generally shows a location of a particular drive (e.g., slot number 1, 2, etc.). The second column provides drive specific information, such as the vendor that manufactured the particular drive (e.g., Seagate, Hitachi, etc.). The next column generally represents a product ID, which may be a particular brand of drive. The next column may implement a device ID column which may represent a particular number of the device in the overall rate (e.g., 26, 27, . . . 32, etc.). The next column illustrates the current version of the firmware installed on the particular drive of a particular row. In the case shown, the device 26 is shown having firmware version 2.1. The device 27 is shown having firmware version 3.10. The device 32 is shown having firmware version 2.05. The next column represents whether a firmware update is needed. If the current firmware to be installed is version 3.1, then device 27 does not need to be updated. In such an example, the devices 26 and 32 do need to be updated. Then the final column shows the power state of the particular drive. In this case, the drive device ID 26 is in the power save mode. Since the firmware update is needed, and the device 26 is in the power save mode, a firmware update may be initiated. For the device ID 27, since an update is not needed, the determination of the power state is not needed (e.g., “don't care”). For the device ID 32, the current firmware version is 2.05, so an update is needed. Since the power state is active, the device ID 32 should wait for a power save condition to occur.

The method 200 may work around the issue where one or more of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n may never enter Power Save mode. For example, one or more critical I/O requests may be continuously (or nearly continuously) running on one or more of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n. In such an example, the management application 107 may be configured to wait for a pre-set time (e.g., 12 hours, but a user may configure the particular number/time of the wait period) for the remaining drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n to enter the Power Save mode. If the remaining drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n do not enter into Power Save mode after the wait period, the management application 107 may start monitoring drive performance using a Drive Performance Monitor (DPM). When the activity of a particular drive 120 a-120 n, 122 a-122 n and/or 124 a-124 n goes less than the pre-set value (e.g., 30%) the management application 107 will push the drive firmware update avoiding any I/O delay.

In general, the method 200 will start when a user intends to update the firmware on one or more of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n. The management utility 107 may be implemented as a storage management application (e.g., MSM, Megacli, etc.). A user may select one or more of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n intended to be updated. The user will normally browse a number of available firmware files and select the firmware file to be used for the update.

The firmware 109 will compare the current firmware version on each of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n to the selected firmware version. If the versions are the same, the particular drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n that have the same firmware version will be dropped from list. The firmware 109 will then automatically create a new list of drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n that need an update.

The management application 107 and/or the firmware 109 will then use the new list to determine which of the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n are in “Power Save” mode. For the drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n which are identified as being in Power Save mode, a firmware update will be implemented. AEN will be generated for the successful firmware update.

After a first pass of updates, the management application 107 and/or the firmware 107 will again update list of remaining drive/drives which are currently not in Power Save mode and also have drive firmware update marked “pending” for these drives. The firmware 109 may then start a timer (e.g., the step 210). The timer may represent a threshold time defined by user as to how long to wait before the remaining drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n enter to “Power Save” mode.

The management application 107 and/or firmware 109 will push the firmware update to drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n that go into Power Save mode within the threshold time. The management application 107 and/or the firmware 109 will drop the update drives 120 a-120 n, 122 a-122 n and/or 124 a-124 n from the list and prepare a new list.

When the threshold time defined by user is over, the management application 107 may implement a DPM (drive performance monitoring) feature to check I/O activity on the remaining drives. The management application 107 may then push a drive firmware update whenever I/O activity is less than 30% (or other threshold) on a drive.

The functions performed by the diagrams of FIGS. 3 and 4 may be implemented using one or more of a conventional general purpose processor, digital computer, microprocessor, microcontroller, RISC (reduced instruction set computer) processor, CISC (complex instruction set computer) processor, SIMD (single instruction multiple data) processor, signal processor, central processing unit (CPU), arithmetic logic unit (ALU), video digital signal processor (VDSP) and/or similar computational machines, programmed according to the teachings of the present specification, as will be apparent to those skilled in the relevant art(s). Appropriate software, firmware, coding, routines, instructions, opcodes, microcode, and/or program, modules may readily be prepared by skilled programmers based on the teachings of the present disclosure, as will also be apparent to those skilled in the relevant art(s). The software is generally executed from a medium or several media by one or more of the processors of the machine implementation.

The present invention may also be implemented by the preparation of ASICs (application specific integrated circuits), Platform ASICs, FPGAs (field programmable gate arrays), PLDs (programmable logic devices), CPLDs (complex programmable logic device), sea-of-gates, RFICs (radio frequency integrated circuits), ASSPs (application specific standard products), one or more monolithic integrated circuits, one or more chips or die arranged as flip-chip modules and/or multi-chip modules or by interconnecting an appropriate network of conventional component circuits, as is described herein, modifications of which will be readily apparent to those skilled in the art(s).

The present invention thus may also include a computer product which may be a storage medium or media and/or a transmission medium or media including instructions which may be used to program a machine to perform one or more processes or methods in accordance with the present invention. Execution of instructions contained in the computer product by the machine, along with operations of surrounding circuitry, may transform input data into one or more files on the storage medium and/or one or more output signals representative of a physical object or substance, such as an audio and/or visual depiction. The storage medium may include, but is not limited to, any type of disk including floppy disk, hard drive, magnetic disk, optical disk, CD-ROM, DVD and magneto-optical disks and circuits such as ROMs (read-only memories), RAMS (random access memories), EPROMs (erasable programmable ROMs), EEPROMs (electrically erasable programmable ROMs), UVPROM (ultra-violet erasable programmable ROMs), Flash memory, magnetic cards, optical cards, and/or any type of media suitable for storing electronic instructions.

The elements of the invention may form part or all of one or more devices, units, components, systems, machines and/or apparatuses. The devices may include, but are not limited to, servers, workstations, storage array controllers, storage systems, personal computers, laptop computers, notebook computers, palm computers, personal digital assistants, portable electronic devices, battery powered devices, set-top boxes, encoders, decoders, transcoders, compressors, decompressors, pre-processors, post-processors, transmitters, receivers, transceivers, cipher circuits, cellular telephones, digital cameras, positioning and/or navigation systems, medical equipment, heads-up displays, wireless devices, audio recording, audio storage and/or audio playback devices, video recording, video storage and/or video playback devices, game platforms, peripherals and/or multi-chip modules. Those skilled in the relevant art(s) would understand that the elements of the invention may be implemented in other types of devices to meet the criteria of a particular application.

While the invention has been particularly shown and described with reference to the preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the scope of the invention. 

1. A method for updating firmware in one or more drives of a drive array, comprising the steps of: (A) initiating a request to apply a firmware update to a plurality of drives in a drive array; (B) determining which of said plurality of drives are in an idle state; (C) sending said firmware update to said drives determined to be in said idle state; and (D) repeating steps (B) and (C) until all of said drives have been updated.
 2. The method according to claim 1, wherein said method further comprises the step of: determining whether one or more of said plurality of drives fails to enter said idle state within a predetermined time; and applying said firmware update if I/O activity in said drive becomes less than a predetermined amount.
 3. The method according to claim 2, wherein said predetermined time is separately determined for each of said plurality of drives.
 4. The method according to claim 1, wherein said drive array comprises a redundant array of inexpensive disks (RAID).
 5. The method according to claim 1, wherein step (A) comprises selecting a sub-set of said plurality of drives to perform said firmware update.
 6. The method according to claim 1, wherein step (A) further comprises selecting a particular firmware file from a plurality of firmware files to apply to each of said plurality of selected drives.
 7. The method according to claim 1, wherein said idle state comprises a state with little or no I/O activity.
 8. The method according to claim 1, wherein said idle state comprises a power down state.
 9. An apparatus for updating firmware in one or more drives of a drive array, comprising the steps of: means for initiating a request to apply a firmware update to a plurality of drives in a drive array; means for determining which of said plurality of drives are in an idle state; means for sending said firmware update to said drives determined to be in said idle state; and means for repeating steps (B) and (C) until all of said drives have been updated.
 10. An apparatus comprising: a management utility on a host computer configured to initiate a request to apply a firmware update to a plurality of drives in an array; and a processing utility on a drive controller configured to (i) determine which of said plurality of drives are in an idle state, (ii) send said firmware update to said drives determined to be in said idle state and (iii) repeat (i) and (ii) until all of said drives have been updated.
 11. The apparatus according to claim 10, wherein said host computer is connected to said controller through a network in a SAN/NAS configuration.
 12. The apparatus according to claim 10, wherein said host computer is connected directly to said controller in a DAS configuration.
 13. The apparatus according to claim 10, wherein said apparatus is further configured to (i) determine whether one or more of said plurality of drives fails to enter said idle state within a predetermined time and (ii) apply said firmware update if I/O activity in said drive becomes less than a predetermined amount.
 14. The apparatus according to claim 13, wherein said predetermined time is separately determined for each of said plurality of drives.
 15. The apparatus according to claim 10, wherein said drive array comprises a redundant array of inexpensive disks (RAID).
 16. The apparatus according to claim 10, wherein said apparatus is further configured to select a sub-set of said plurality of drives to perform said firmware update.
 17. The apparatus according to claim 10, wherein said apparatus is further configured to select a particular firmware file from a plurality of firmware files to apply to each of said plurality of selected drives.
 18. The apparatus according to claim 10, wherein said idle state comprises a state with little or no I/O activity.
 19. The apparatus according to claim 10, wherein said idle state comprises a power down state. 